|
|
Hi Kerwin Additionally, this log does not occur in INTEK STB. there seems to be something different. Attached is the package version for FW in the field version of INTEK STB. (INTEK-package_version.txt) Please review what could be the cause of the issue. SKB considers this error log important. so we need a quick update on this log. Please check it Thank you YK.Jung INTEK-package_version.txt (4,869 bytes) |
|
|
Hi YK, The version of Webview on BFX-AT100 is the same as INTEK STB. (90.0.4430.91) But from your information, you said that INTEK STB does not have this error log, so how can you confirm that the root cause is from Webview package? Do you know how to reproduce it? Based on past experience, before we post this issue on the issue tracker, we need to know how to reproduce it and check if this issue can be reproduced on the Aml reference board. Thanks |
|
|
Hi Jason There is no evidence that webview is a root cause. SKB talked about whether it would be related to web view. I don't know how to reproduce the error log. in my case, the following message is output. 03-16 10:06:42.411 6121 6121 I chromium: [6121:6121:INFO:robot_account_auth_manager.cc(492)] JWT expiry in 3600 seconds And we don't know how to reproduce it, So please ask Google what the error means and when this error log occurs. Thank you YK.Jung |
|
|
Hi YK, You have given us too little information. (only 1 line of log) As you know, we are working on "Google Account Sync cause Android restarting" issue with Google TAM. I think you should be very clear about the process If Google TAM can NOT gather enough information. He don't know how to check it with Webview team. Thanks, Jason |
|
|
Hi Jason Attached is the picture file. kibana_2022-0316_1.PNG Please check it This error message does not occur with INTEK STB. Currently, we don't know how to reproduce, and we don't have any clear information. And the problem is that this error message only occurs with FXN STB. I think , we need to know what this string means so that we can reproduce it. "JWT signing failed. Retrying after 5 secs." Please ask Google what this error string means and how it can occur. Thanks YK.Jung kibana_2022-0316_1.PNG (100,427 bytes) |
|
|
Hi YK, I've checked the rule of issue tracker, we MUST collect the following information Description Field MUST provide the details of the issue ● Testing environment ○ Android OS version ○ SW configuration (reversion of relevant APKs, etc) ○ HW configuration (refer to your Project Tracker HW matrix) ○ Environment details as relevant (region, language, network setup) ● Steps to reproduce the issue ● Expected and actual results ● Failure rate ● Reproducibility on an SOC reference design, Android TV developer device (ADT-X) or other in-market Android TV devices ● Bug report ○ Highlight via text snippet any relevant error messages to aid investigation |
|
|
Hi Jason SKB and Jeff were discussed in advance. Jeff suggested that we communicate this issue on google issue tracker. because Jeff can't use SKB jira. I have captured the contents of the email I received from SKB. (SKB_email.PNG) Therefore, the content of this issue can be discussed in the google issue tracker. Please also upload the VoC log in the JIRA to issue tracker ( assign it to jeff. ) ====== VoC logs ====== *** JWT signing failed. Retrying after 5 secs *** 0130000037_20220224_28_CD_C4_FA_F3_7B.zip 0130000037_20220224_28_CD_C4_FD_5E_2C.zip 0130000037_20220224_28_CD_C4_FD_19_BF.zip ======================================== Thank you YK.Jung SKB_email.PNG (72,265 bytes) |
|
|
Hi YK, Could you let me know which file should be upload in each zip. "Highlight via text snippet any relevant error messages to aid investigation " We must provide a number in each logcat to help Google investigate. For example: ***.zip, mainlog.1, line number: xxxx |
|
|
Hi Jason I haven't used Google Issue tracker , so I don't understand. Please check the following information and apply it according to the issue tracker format and register it. ======================= The following warning message has been observed from the user STBs but we don't understand the content of this warning message. Line number : 257 0130000037_20220224_28_CD_C4_FA_F3_7B/main.log.1:02-23 14:57:13.052 3490 3530 W WVCdm : [device_files.cpp(1230):RetrieveHashedFile] DeviceFiles::RetrieveHashedFile: /data/vendor/mediadrm/IDM1013/L1/cert.bin does not exist Line number : 276 0130000037_20220224_28_CD_C4_FA_F3_7B/main.log.1:02-23 14:57:13.177 5454 5454 W chromium: [5454:5454:WARNING:robot_account_auth_manager.cc(491)] JWT signing failed. Retrying after 5 secs. .. Line number : 38 0130000037_20220224_28_CD_C4_FD_5E_2C/main.log.1:02-23 15:29:40.101 3493 6104 W WVCdm : [device_files.cpp(1230):RetrieveHashedFile] DeviceFiles::RetrieveHashedFile: /data/vendor/mediadrm/IDM1013/L1/cert.bin does not exist Line number : 52 0130000037_20220224_28_CD_C4_FD_5E_2C/main.log.1:02-23 15:29:34.963 5694 5694 W chromium: [5694:5694:WARNING:robot_account_auth_manager.cc(491)] JWT signing failed. Retrying after 5 secs. .. 1) Why does this warning message occur? 2) I would like to know which service or module this message is related to. 3) What operational problems occurred when this warning message was displayed? ================================================================================= Thank you YK.Jung |
|
|
Hi YK, Already post it on https://partnerissuetracker.corp.google.com/u/1/issues/225115759 |
|
|
Hi YK, The comment from Google is as follows, Please get the latest Webview apk (WebViewGoogle.apk and TrichromeLibrary.apk) from the GTVS Git and give to SKB. Version:99.0.4844.73 Please check the attachment. |
|
2022-03-24 11:24 developer |
|
|
|
Hi Jason we found a way to reproduce the issue. 1) burning Smart3 Android 9 ( v15.520.8 ) 2) login google account 3) update Smart3 Android 10 ( v15.532.20) 4) JWT warning message is observed. Additionally, the JWT warning message disappears when you reset Google in the system settings at Android 10. It seems to be caused by the any google information(?) in Android 9. Please test it once again and update Google issue tracker about this situation. Thank you YK.Jung |
|
|
Hi Jason The above information is incorrect. We haven't found the exact reproduction method yet. First of all, I guess it's due to the update of the Android version or provisioning ( This issue does not occur INTEK and Innopia ) Please check how to reproduce this issue in FXN as well. Thank you YK.Jung |
|
|
Hi YK, I found the reproduce steps as follows, 1. Use Android 9 device 2. Open PlayStore, update Chromecast built-in to the latest version (1.56.276477). After updating the Chromecast, we confirmed that the YouTube casting function is working normally. 3. Upgrade device to Android 10 by OTA After boot complete, we can see the following messages in logcat every 5 seconds. We found that the YouTube Casting function doesn't work. 02-23 14:57:13.177 5454 5454 I chromium: [5454:5454:INFO:application_identification_settings.cc(1442)] Missing signature, return empty JWT 02-23 14:57:13.177 5454 5454 W chromium: [5454:5454:WARNING:robot_account_auth_manager.cc(491)] JWT signing failed. Retrying after 5 secs. 4. Reboot device -> We can still see these error messages and the YouTube Casting function is still not working. 5. Open TvSettings > Apps > Chromecast-builtin > Clear data -> We will no longer see the error messages. 6. Reboot device -> YouTube Casting function works normally. Please forwarded this troubleshooting step to SKB. I've updated this information on issue tracker. Thanks, |
|
|
Hi YK, I have done another test as below, 1. Use Android 9 device 2. upgraded STB to Android 10 by OTA After boot complete, We didn't see JWT "signing failed. Retrying after 5 secs" in logcat, but we saw the following error messages were printed continuously in logcat (YT Casting function is not working at this time.) 04-01 19:07:34.915 7516 7516 I chromium: [7516:7516:INFO:metrics_recorder.cc(286)] cast event: Cast.Sign.Error.SignatureEmpty 04-01 19:07:34.915 7516 7516 I chromium: [7516:7516:INFO:application_identification_settings.cc(1334)] CreateJwt completed; running all done signing callbacks. 04-01 19:07:35.008 7516 7591 I chromium: [7516:7591:INFO:jni_client_auth_creds_mediadrm.cc(222)] JniRsaSigner::SignHash: failed to openSession. 04-01 19:07:35.008 7516 7591 I chromium: [7516:7591:INFO:metrics_recorder.cc(286)] cast event: Cast.WidevineCastAuth.Error.SessionOpenFailed 04-01 19:07:35.008 7516 7591 E chromium: [7516:7591:ERROR:client_auth_creds.cc(107)] Could not sign message in SSLPrivateKeyCastInternal::Sign! 3. Open PlayStore, update Chromecast-builtin (mediashell) to the latest version (1.56.276477). After updating mediashell, we can see the following messages in logcat every 5 seconds. We found that the YT Casting function still doesn't work. 04-01 19:12:30.019 15505 15546 I chromium: [15505:15546:INFO:jni_client_auth_creds_mediadrm.cc(222)] JniRsaSigner::SignHash: failed to openSession. 04-01 19:12:30.020 15505 15546 I chromium: [15505:15546:INFO:metrics_recorder.cc(188)] cast event: Cast.WidevineCastAuth.Error.SessionOpenFailed 04-01 19:12:30.021 15505 15546 E chromium: [15505:15546:ERROR:client_auth_creds.cc(107)] Could not sign message in SSLPrivateKeyCastInternal::Sign! 04-01 19:12:30.021 15505 15505 I chromium: [15505:15505:INFO:metrics_recorder.cc(188)] cast event: Cast.Sign.Error.SignatureEmpty 04-01 19:12:30.021 15505 15505 I chromium: [15505:15505:INFO:application_identification_settings.cc(1437)] CreateJwt completed; running all done signing callbacks. 04-01 19:12:30.021 15505 15505 I chromium: [15505:15505:INFO:application_identification_settings.cc(1442)] Missing signature, return empty JWT 04-01 19:12:30.021 15505 15505 W chromium: [15505:15505:WARNING:robot_account_auth_manager.cc(491)] JWT signing failed. Retrying after 5 secs. 4. Reboot device -> We can still see these error messages and the YT Casting function is still not working. 5. Clear Chromecast-builtin Data (Open TvSettings > Apps > Chromecast-builtin > Clear data) -> We will no longer see the "JWT signing failed. Retrying after 5 secs." error messages 6. Reboot device -> YT Casting function works normally. Please reproduce it on your side and share your result. |
|
|
Hi YK, I have checked this issue with Amlgoic, it looks known issue, Other customer also reported this issue to Amlogic before, Amlogic has workaround to fix it Please check the attachment (0001-releasettools-delete-google-data-1-1.patch) This patch will delete the data of ChromeCast during OTA. I have tried to apply it in device/amlogic folder and rebuild the new OTA file to verify this issue. After applying this patch, this patch will cause OTA fail. My test steps is as follows, 1. Burning 15.520.8 Android P image 2. OTA to the latest 15.532 code (Android Q) -> Confirm the casting is not working 3. OTA to the latest 15.532 code + Amlogic patch -> OTA fail, Could you forward this patch and check it with Middle ware, because middle ware is in charge of OTA process. I think middleware can check this patch with Amlogic directly. Thanks, Jason 0001-releasettools-delete-google-data-1-1.patch (1,323 bytes) |
|
|
Hi Jason Now this issue is being discussed in jira below. https://jira.skbroadband.com/browse/BTVD-20628 I have updated the information you told me. I will let you know when I receive the information from SPTEK. Thank you YK.Jung |
|
|
Hi Jason SPTEK says: To find out why OTA fails, Please send the log file in the path below. /cache/recovery Please send me the file(/cache/recovery/). Thank you YK.Jung |
|
|
Hi YK, Please check the attachment bugreport-BFX_AT100-QTT5.200429.010-2022-04-11-11-05-39.zip. Thanks, Jason |
|
|
Hi Jason This issue occurs before MW, so Amlogic is checking it. Amlogic says it's probably caused by security Please change the security mode to permissive mode and test it. console:/ # setenforce 0 console:/ # getenforce Permissive Thank you YK.Jung |
|
|
Hi YK, The issue is in recovery mode, How to disable selinux in recovery mode? And SKB released user-build to field user. How to disable selinux in usebuild? |
|
|
Hi Jason I got an answer from amlogic. and it seems to be working OK. https://jira.skbroadband.com/browse/BTFAML-1059 1) please apply below code. ( I think you can apply it yourself. ) diff --git a/releasetools.py b/releasetools.py index 1a8a881..4477576 100755 --- a/releasetools.py +++ b/releasetools.py @@ -225,6 +225,17 @@ package_extract_file("vbmeta.img", "/dev/block/vbmeta");""") info.script.AppendExtra('set_update_stage("0");') info.script.AppendExtra('endif;') + info.script.AppendExtra('ui_print("rm mediashell...");') + info.script.AppendExtra('ui_print("START...");') + info.script.AppendExtra('run_program("/sbin/busybox", "mount", "-t", "ext4", "dev/block/data", "/data/");') +# info.script.AppendExtra('mount("ext4", "EMMC", "/dev/block/data", "/data");') + info.script.AppendExtra('ui_print("mount success");') + info.script.AppendExtra('run_program("/sbin/busybox", "ls", "/data/", "-al");') + info.script.AppendExtra('run_program("/sbin/busybox", "rm", "/data/data/com.google.android.apps.mediashell", "-rf");') + info.script.AppendExtra('ui_print("rm done");') + info.script.AppendExtra('unmount("/data");') + info.script.AppendExtra('ui_print("umount done");') + SetBootloaderEnv(info.script, "upgrade_step", "1") SetBootloaderEnv(info.script, "force_auto_update", "false") 2) Create an image with 1) applied. Copy the image to USB and connect it to STB. 3) Change the selinux mode at recovery mode. ( uboot ) Test command for selinux >>>> g12a_u212_v1# setenv EnableSelinux permissive;saveenv;reset .. g12a_u212_v1# run recovery_from_flash ==> proceed with the upgrade with the image file on the USB. Please check it. Thank you YK.Jung |
|
|
Hi YK, How do you disable selinux in recovery mode in official fw? For Testing, I think that we can use command to disable selinux in uboot. But How to apply it in official FW? As far as I know, Remove chromcast data in reocvery mode is not official patch, Amlogic didn't push this patch to their git trunk. It looks like there is Selinux issue and Amlogic has not fix it yet. I guess other OEMs used trobbleshotting method (clearing chomecast data by user or sending remote command to clear chromecast data by operator) when user upgrade from 9 to 10. Because modifying anything in recovery mode is very sensitive. It's related to OTA. Could you discuss it with Amlogic or SKB? Thanks, Jason |
|
|
Hi YK, Please refer to the Google Mr. Jeff's comments below, "On the Amlogic bug, Mediashell engineer informed that the only option is deleting the data of mediashell. I have communicated this to SKB. Closing the bug." |
|
|
no activity for this issue |
- yk.jung ( (ALTech) Younkwang Jung ) developer
